System and method for providing network security to mobile devices

ABSTRACT

A small piece of hardware connects to a mobile device and filters out attacks and malicious code. Using the piece of hardware, a mobile device can be protected by greater security and possibly by the same level of security offered by its associated corporation/enterprise. In one embodiment, a mobile security system includes a connection mechanism for connecting to a data port of a mobile device and for communicating with the mobile device; a network connection module for acting as a gateway to a network; a security policy for determining whether to forward content intended for the mobile device to the mobile device; and a security engine for executing the security policy.

PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No.15/352,553, filed Nov. 15, 2016 and entitled “System and Method forProviding Network Security to Mobile Devices,” which is a continuationU.S. patent application Ser. No. 14/092,756, filed Nov. 27, 2013 andentitled “System and Method for Providing Network Security to MobileDevices,” now U.S. Pat. No. 9,497,622, which is a continuation of U.S.patent application Ser. No. 13/735,836, filed Jan. 7, 2013 and entitled“System and Method for Providing Network Security to Mobile Devices,”now U.S. Pat. No. 8,627,452, which is a continuation of U.S. patentapplication Ser. No. 11/376,919, filed Mar. 15, 2006 and entitled“System and Method for Providing Network Security to Mobile Devices,”now U.S. Pat. No. 8,381,297, which claims priority to U.S. ProvisionalPatent Application Ser. No. 60/750,326, filed Dec. 13, 2005 and entitled“Personal Security Appliance.” All of the above applications are herebyincorporated by reference herein.

TECHNICAL FIELD

This invention relates generally to network security, and moreparticularly provides a system and method for providing network securityto mobile devices.

BACKGROUND

The internet is an interconnection of millions of individual computernetworks owned by governments, universities, nonprofit groups, companiesand individuals. While the internet is a great source of valuableinformation and entertainment, the internet has also become a majorsource of system damaging and system fatal application code, such as“viruses,” “spyware,” “adware,” “worms,” “Trojan horses,” and othermalicious code.

To protect users, programmers design computer and computer-networksecurity systems for blocking malicious code from attacking bothindividual and network computers. On the most part, network securitysystems have been relatively successful. A computer that connects to theinternet from within an enterprise's network typically has two lines ofdefense. The first line of defense includes a network security system,which may be part of the network gateway, that includes firewalls,anti-virus, anti-spyware and content filtering. The second line ofdefense includes individual security software on individual machines,which is not typically as secure as the network security system and isthus more vulnerable to attacks. In combination, the first and secondlines of defense together provide pretty good security protection.However, when a device connects to the internet without the interveningnetwork security system, the device loses its first line of defense.Thus, mobile devices (e.g., laptops, desktops, PDAs such as RIM'sBlackberry, cell phones, any wireless device that connects to theinternet, etc.) when traveling outside the enterprise network are morevulnerable to attacks.

FIG. 1 illustrates an example network system 100 of the prior art.Network system 100 includes a desktop 105 and a mobile device 110, eachcoupled to an enterprise's intranet 115. The intranet 115 is coupled viaa network security system 120 (which may be a part of the enterprise'sgateway) to the untrusted internet 130. Accordingly, the desktop 105 andmobile device 110 access the internet 130 via the network securitysystem 120. A security administrator 125 typically manages the networksecurity system 120 to assure that it includes the most current securityprotection and thus that the desktop 105 and mobile device 110 areprotected from malicious code. Demarcation 135 divides the trustedenterprise 140 and the untrusted public internet 130. Because thedesktop 105 and the mobile device 110 are connected to the internet 130via the network security system 120, both have two lines of defense(namely, the network security system 120 and the security softwareresident on the device itself) against malicious code from the internet130. Of course, although trusted, the intranet 115 can also be a sourceof malicious code.

FIG. 2 illustrates an example network system 200 of the prior art, whenthe mobile device 110 has traveled outside the trusted enterprise 140and reconnected to the untrusted internet 130. This could occur perhapswhen the user takes mobile device 110 on travel and connects to theinternet 130 at a cybercafe, at a hotel, or via any untrusted wired orwireless connection. Accordingly, as shown, the mobile device 110 is nolonger protected by the first line of defense (by the network securitysystem 120) and thus has increased its risk of receiving malicious code.Further, by physically bringing the mobile device 110 back into thetrusted enterprise 140 and reconnecting from within, the mobile device110 risks transferring any malicious code received to the intranet 115.

As the number of mobile devices and the number of attacks grow, mobilesecurity is becoming increasingly important. The problem was emphasizedin the recent Info-Security Conference in New York on Dec. 7-8, 2005.However, no complete solutions were presented.

There is a need for personal security appliances capable of providinglevels of network security as provided by enterprise network securitysystems.

SUMMARY

An embodiment of the present invention uses a small piece of hardwarethat connects to a mobile device and filters out attacks and maliciouscode. The piece of hardware may be referred to as a “mobile securitysystem” or “personal security appliance.” Using the mobile securitysystem, a mobile device can be protected by greater security andpossibly by the same level of security offered by its associatedcorporation/enterprise.

In an embodiment, a mobile security system includes a connectionmechanism for connecting to a data port of a mobile device and forcommunicating with the mobile device; a network connection module foracting as a gateway to a network; a security policy for determiningwhether to forward content intended for the mobile device to the mobiledevice; and a security engine for executing the security policy.

The connection mechanism may include at least one of a USB connector, aPCMCIA connector, an Ethernet connector, and a BlueTooth communicationmodule. The network connection module may include a network interfacecard that implements WiFi, WiMAX, GPRS, GSM, UMTS, CDMA, Generation 3,other cell phone internet connection protocols, etc. The security enginemay include at least one of an antivirus engine, an antispyware engine,a firewall engine, an IPS/IDS engine, a content filtering engine, amultilayered security monitor, a bytecode monitor, and a URL monitor.The security policy may perform weighted risk analysis based on contenttype, content source, content category, or historical actions of theuser. The remote management module may be capable of receiving securitypolicy updates, security engine updates, and security data updates(including malicious content signatures). The mobile security system mayinclude a distribution module capable of forwarding updates to othermobile security systems, and/or a backup module capable of storing atleast a portion of the boot sector of the mobile device should the bootsector of the mobile device become compromised. The mobile securitysystem may include a remote configuration module capable ofcommunicating with a wizard, the wizard being in communication with anenterprise network security system, the wizard capable of substantiallyautomatic generation of policies and data based on the policies and dataon the enterprise network security system, the remote configurationmodule capable of installing the policies and data generated by thewizard. The mobile security system may include a preboot memory that isnot accessible during runtime, the preboot memory storing a copy of atleast a portion of the operating system of the mobile security system,the mobile security system being configured to load the operating systemportion every time the mobile security system is rebooted.

In another embodiment, a method comprises receiving a network connectionrequest from a mobile device outside of a trusted network; acting as agateway to a network on behalf of the mobile device; receivinginformation intended for the mobile device from the network; anddetermining whether to forward the information to the mobile device inaccordance with a security policy.

In another embodiment, a mobile security system comprises means foracting as a gateway to a network on behalf of a mobile device outside ofa trusted network; receiving information intended for the mobile devicefrom the network; and determining whether to forward the information tothe mobile device in accordance with a security policy.

In yet another embodiment, a method comprises receiving internet trafficon a mobile device via a wireless connection; redirecting the internettraffic at the kernel level to a mobile security system; scanning theinternet traffic for violations of a security policy; cleaning theinternet traffic of any violations of the security policy to generatecleaned internet traffic; and sending the cleaned internet traffic tothe mobile device for execution.

In still another embodiment, a system comprises a wireless networkinterface card on a mobile device for receiving internet traffic; akernel-level redirector on the mobile device for redirecting theinternet traffic at the kernel level to a mobile security system; asecurity engine for scanning the internet traffic for violations of asecurity policy and for cleaning the internet traffic of any violationsof the security policy to generate cleaned internet traffic; and aconnection mechanism for receiving the redirected internet traffic fromthe kernel-level redirector and for sending the cleaned internet trafficto the mobile device for execution.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a prior art network system in a firststate.

FIG. 2 is a block diagram of a prior art network system in a secondstate.

FIG. 3 is a block diagram of a network system in accordance with anembodiment of the present invention.

FIG. 4 is a block diagram illustrating details of a computer system inaccordance with an embodiment of the present invention.

FIGS. 5 and 5A are block diagrams illustrating details of the mobilesecurity system in accordance with an embodiment of the presentinvention.

FIG. 6 is a block diagram illustrating details of the mobile securitysystem in accordance with a Microsoft Windows' embodiment.

FIG. 7 is a block diagram illustrating details of a smart policyupdating system in accordance with an embodiment of the presentinvention.

FIG. 8 is a block diagram illustrating details of network securitymeasures relative to the OSI layers.

FIG. 9 is a block diagram illustrating details of the communicationtechnique for spreading security code to the mobile security systems.

FIGS. 10A-10C are block diagrams illustrating various architectures forconnecting a mobile device to a mobile security system, in accordancewith various embodiments of the present invention.

DETAILED DESCRIPTION

The following description is provided to enable any person skilled inthe art to make and use the invention, and is provided in the context ofa particular application and its requirements. Various modifications tothe embodiments may be possible to those skilled in the art, and thegeneric principles defined herein may be applied to these and otherembodiments and applications without departing from the spirit and scopeof the invention. Thus, the present invention is not intended to belimited to the embodiments shown, but is to be accorded the widest scopeconsistent with the principles, features and teachings disclosed herein.

An embodiment of the present invention uses a small piece of hardwarethat connects to a mobile device and filters out attacks and maliciouscode. The piece of hardware may be referred to as a “mobile securitysystem” or “personal security appliance.” Using the mobile securitysystem, a mobile device can be protected by greater security andpossibly by the same level of security offered by its associatedcorporation/enterprise.

FIG. 3 illustrates a network system 300 in accordance with an embodimentof the present invention. Network system 300 includes a desktop 305, afirst mobile device 310 a, and a second mobile device 310 b. The firstmobile device 310 a is illustrated as within the enterprise network 340at this time and is coupled via a mobile security system 345 a to theenterprise's intranet 315. The desktop 305 and second mobile device 310b are also within the enterprise network 340 but in this embodiment arecoupled to the intranet 315 without an intervening mobile securitysystem 345 such as mobile security system 345 b. The intranet 315 iscoupled via a network security system 320 (which may be part of theenterprise's gateway) to the untrusted internet 330. Accordingly, thefirst mobile device 310 a, the second mobile device 310 b and thedesktop 305 access the untrusted internet 330 via the network securitysystem 320. Each may also be protected by a personal security systemresident thereon (not shown). A third mobile device 310 c is currentlyoutside the enterprise network 340 and is coupled via a mobile securitysystem 345 b to the untrusted internet 330. The third mobile device 310may be in use by an employee of the trusted enterprise 340 who iscurrently on travel. A security administrator 325 manages the mobilesecurity system 345 a, the mobile security system 345 b, and the networksecurity system 320 to assure that they include the most currentsecurity protection. One skilled in the art will recognize that the samesecurity administrator need not manage the various devices. Further, thesecurity administrator could be the user and need not be within thetrusted enterprise 340.

Demarcation 335 divides the trusted enterprise 340 and the untrustedpublicly accessible internet 330. Each of mobile device 310 a, 310 b and310 c may be referred to generically as mobile device 310, although theyneed not be identical. Each mobile security system 345 a and 345 b maybe referred to generically as mobile security system 345, although theyneed not be identical.

As shown, although the mobile device 310 c has traveled outside thetrusted enterprise 340, the mobile device 310 c connects to theuntrusted internet 330 via the mobile security system 345 b and thusretains two lines of defense (namely, the mobile security system 345 band the security software resident on the device itself). In thisembodiment, the mobile security system 345 effectively acts as a mobileinternet gateway on behalf of the mobile device 310 c. In an embodiment,the mobile security system 345 may be a device dedicated to networksecurity. In an embodiment, each mobile security system 345 may supportmultiple mobile devices 310, and possibly only registered mobile devices310, e.g., those belonging to enterprise 340.

Each mobile security system 345 (e.g., 345 a, 345 b) may be a miniatureserver, based on commercial hardware (with Intel's Xscale as the core),Linux OS and network services, and open-source firewall, IDS/IPS andantivirus protection. The mobile security system 345 may be based on ahardened embedded Linux 2.6.

In this embodiment, because the security administrator 325 is capable ofremotely communicating with the mobile security system 345 b, IT canmonitor and/or update the security policies/data/engines implemented onthe mobile security system 345 b. The security administrator 325 cancentrally manage all enterprise devices, remotely or directly. Further,the security administrator 325 and mobile security systems 345 caninteract to automatically translate enterprise security policies intomobile security policies and configure mobile security systems 345accordingly. Because the mobile security system 345 may be generatedfrom the relevant security policies of the enterprise 340, the mobiledevice 310 c currently traveling may have the same level of protectionas the devices 305/310 within the trusted enterprise 340.

The mobile security system 345 may be designed as an add-on to existingsoftware security or to replace all security hardware and software on atraveling mobile device. These security applications will preferablyoperate on different OSI layers to provide maximum security andmalicious code detection, as shown in the example system illustrated inFIG. 8. Operating on the lower OSI layers and doing TCP/IP packetsanalysis only (by screening firewall or router packets) would miss virusand/or worm behavior. Also, many modern viruses use mobile codeimplemented on a “higher” level than the 7^(th) OSI layer(Application—HTTP, FTP, etc.) and therefore cannot be interpreted at thepacket layer nor at the application layer. For example, applyingantivirus analysis only at the session or transport layer on a maliciousJava Script (that is included in an HTML page), trying to match thesignature with packets and without understanding the content type (JavaScript), will not detect the malicious nature of the Java Script. Tooffer greater protection, the mobile security system 345 may act ascorporate class security appliance and engage different securityapplications based on the content type and the appropriate OSI layers,(or even a “higher” level if content is encapsulated in the applicationlayer). The mobile security system 345 may be configured to performcontent analysis at different OSI layers, e.g., from the packet level tothe application level. It will be appreciated that performing deepinspection at the application level is critical to detect maliciouscontent behavior and improve detection of viruses, worms, spyware,Trojan horses, etc. The following software packages may be implementedon the mobile security system 345:

-   -   Firewall and VPN—including stateful and stateless firewalls,        NAT, packet filtering and manipulation, DOS/DDOS, netfilter,        isolate user mobile devices from the internet and run VPN        program on the device, etc.    -   Optional web accelerator and bandwidth/cache management based on        Squid.    -   IDS/IPS—Intrusion detection and prevention system based on        Snort. Snort is an open source network intrusion prevention and        detection system utilizing a rule-driven language, which        combines the benefits of signature, protocol- and anomaly-based        inspections.    -   Antivirus and antispyware based on ClamAV; additional AV and AS        engines, e.g., McAfee, Kaspersky, Pandamay, may be offered for        additional subscription fees.    -   Malicious Content Detection—on the fly heuristics that perform        content analysis to detect malicious content before having        signatures. This will be based on a rule base and updated rules        and will be content dependent scanning.    -   URL Categorization Filtering—based on a commercial engine, such        as Surfcontrol, Smart Filters or Websense. May provide around 70        categories of URLs such as gambling, adult content, news,        webmail, etc. The mobile device 345 may apply different security        policies based on the URL category, e.g., higher restriction and        heuristics for Gambling or Adult content web sites, etc.

FIG. 4 is a block diagram illustrating details of an example computersystem 400, of which each desktop 305, mobile device 310, networksecurity system 320, mobile security system 345, and securityadministrator 325 may be an instance. Computer system 400 includes aprocessor 405, such as an Intel Pentium® microprocessor or a MotorolaPower PC® microprocessor, coupled to a communications channel 410. Thecomputer system 400 further includes an input device 415 such as akeyboard or mouse, an output device 420 such as a cathode ray tubedisplay, a communications device 425, a data storage device 430 such asa magnetic disk, and memory 435 such as Random-Access Memory (RAM), eachcoupled to the communications channel 410. The communications interface425 may be coupled directly or via a mobile security system 345 to anetwork such as the internet. One skilled in the art will recognizethat, although the data storage device 430 and memory 435 areillustrated as different units, the data storage device 430 and memory435 can be parts of the same unit, distributed units, virtual memory,etc.

The data storage device 430 and/or memory 435 may store an operatingsystem 440 such as the Microsoft Windows XP, the IBM OS/2 operatingsystem, the MAC OS, UNIX OS, LINUX OS and/or other programs 445. It willbe appreciated that a preferred embodiment may also be implemented onplatforms and operating systems other than those mentioned. Anembodiment may be written using JAVA, C, and/or C++ language, or otherprogramming languages, possibly using object oriented programmingmethodology.

One skilled in the art will recognize that the computer system 400 mayalso include additional information, such as network connections,additional memory, additional processors, LANs, input/output lines fortransferring information across a hardware channel, the internet or anintranet, etc. One skilled in the art will also recognize that theprograms and data may be received by and stored in the system inalternative ways. For example, a computer-readable storage medium (CRSM)reader 450 such as a magnetic disk drive, hard disk drive,magneto-optical reader, CPU, etc. may be coupled to the communicationsbus 410 for reading a computer-readable storage medium (CRSM) 455 suchas a magnetic disk, a hard disk, a magneto-optical disk, RAM, etc.Accordingly, the computer system 400 may receive programs and/or datavia the CRSM reader 450. Further, it will be appreciated that the term“memory” herein is intended to cover all data storage media whetherpermanent or temporary.

FIG. 5 is a block diagram illustrating details of the mobile securitysystem 345 in accordance with an embodiment of the present invention.Mobile security system 345 includes adapters/ports/drivers 505, memory510, a processor 515, a preboot flash/ROM memory module 520 storing asecure version of the mobile security system's operating system andother applications, network connection module 525, security engines 530,security policies 535, security data 540, remote management module 550,distribution module 555, and backup module 560. Although these modulesare illustrated as within the mobile security system 345, one skilled inthe art will recognize that many of them could be located elsewhere,e.g., on the security administrator 325 or on third-party systems incommunication with the mobile security system 345. The mobile securitysystem 345 may be in a pocket-size, handheld-size or key-chain sizehousing, or possibly smaller. Further, the mobile security system 345may be incorporated within the mobile device 310.

The adapters/ports/drivers 505 include connection mechanisms (includingsoftware, e.g., drivers) for USB, Ethernet, WiFi, WiMAX, GSM, CDMA,BlueTooth, PCMCIA and/or other connection data ports on the mobilesecurity system 345. In one embodiment, the adapters/ports/drivers 505may be capable of connection to multiple devices 310 to provide networksecurity to the multiple devices 310.

Memory 510 and processor 515 execute the operating system andapplications on the mobile security system 345. In this example, thepreboot flash 520 stores the operating system and applications. At boottime, the operating system and applications are loaded from the prebootflash 520 into memory 510 for execution. Since the operating system andapplications are stored in the preboot flash 520, which cannot beaccessed during runtime by the user, the operating system andapplications in the preboot flash 520 are not corruptible. Should thecopy of the operating system and applications in memory 510 becorrupted, e.g., by malicious code, the operating system andapplications may be reloaded into the memory 510 from the preboot flash520, e.g., upon restart. Although described as stored within the prebootflash 520, the OS and applications can be securely stored within otherread-only memory devices, such as ROM, PROM, EEPROM, etc.

As shown in FIG. 5A, memory (including memory 510 and preboot flash 520)on the mobile security system 345 may be divided into the followingzones: read only memory 570; random access memory 575 for storing a copyof the OS, kernel and security applications; runtime environment 580;and database 585 for storing application data, log files, etc. Upon each“hard” restart, the boot loader (resident in read only memory 570) ofthe mobile security system 345 copies the kernel and securityapplications (a fresh unchanged copy) from read only memory 570 torandom access memory 575. This causes a clean version of the OS andapplications to be loaded into random access memory 575 each time. Thatway, if a special attack on mobile security system 345 is developed, theattack will be unable to infect the system, since the OS andapplications are precluded from accessing read only memory 570 duringruntime. Further, any attack that does reach memory 510 will be able torun only once and will disappear upon a hard restart. A triggeringmechanism may be available to restart the mobile security system 345automatically upon infection detection.

The network connection module 525 enables network connection, e.g., tothe internet 330 or the intranet 315 via network communicationhardware/software including WiFi, WiMAX, CDMA, GSM, GPRS, Ethernet,modem, etc. For example, if the mobile device 310 wishes to connect tothe internet 330 via a WiFi connection, the adapters/ports/drivers 505may be connected to the PCI port, USB port or PCMCIA port of the mobiledevice 310, and the network connection module 525 of the mobile securitysystem 345 may include a WiFi network interface card for connecting towireless access points. Using the network connection module 425, themobile security system 345 may communicate with the network as a securegateway for the mobile device 310. Other connection architectures aredescribed in FIGS. 10A-10C.

The security engines 530 execute security programs based on the securitypolicies 535 and on security data 540, both of which may be developed byIT managers. Security engines 530 may include firewalls, VPN, IPS/IDS,anti-virus, anti-spyware, malicious content filtering, multilayeredsecurity monitors, Java and bytecode monitors, etc. Each security engine530 may have dedicated security policies 535 and security data 540 toindicate which procedures, content, URLs, system calls, etc. the engines530 may or may not allow. The security engines 530, security policies535 and security data 540 may be the same as, a subset of, and/ordeveloped from the engines, policies and data on the network securitysystem 320.

To provide a higher security level provided by antivirus and antispywaresoftware, the security engines 530 on each mobile security system 345may implement content analysis and risk assessment algorithms. Operatingfor example at OSI Layer 7 and above (mobile code encapsulated withinLayer 7), these algorithms may be executed by dedicated High RiskContent Filtering (HRCF) that can be controlled by a rules engine andrule updates. The HRCF will be based on a powerful detection librarythat can perform deep content analysis to verify real content types.This is because many attacks are hidden within wrong mime types and/ormay use sophisticated tricks to present a text file type to a dangerousactive script or ActiveX content type. The HRCF may integrate with a URLcategorization security engine 530 for automatic rule adjustment basedon the URL category. In one embodiment, when the risk level increases(using the described mechanism) the mobile security system 345 mayautomatically adjust and increase filtering to remove more activecontent from the traffic. For example, if greater risk is determined,every piece of mobile code, e.g., Java script, VB script, etc. may bestripped out.

Three aspects for integration with corporate policy server legacysystems include rules, LDAP and active directory, and logging andreporting as discussed below. In one embodiment, a policy import agentrunning on the security administrator 325 will access the rule base ofCheckpoint Firewall-1 and Cisco PIX Firewalls and import them into alocal copy. A rule analysis module will process the important rules andwill offer out-of-the-box rules and policies for mobile security systems345. This proposed policy will offer all mobile security systems 345 abest fit of rules that conform the firewall policy of the enterprise340. The agent will run periodically to reflect any changes and generateupdates for mobile security system 345 policies 535. The LDAP and ActiveDirectory may be integrated with the directory service to maintainmobile security system 345 security policies 535 that respond to theenterprise's directory definitions. For example, a corporate policy forLDAP user Group “G” may automatically propagate to all mobile securitysystems 345 in “G” group. Mobile security system 345 local logs andaudit trails may be sent in accordance to a logging and reporting policyto a central log stored at the security administrator 325. Using a webinterface, IT may be able to generate reports and audit views related toall mobile device 310 users, their internet experiences, and attempts tobring infected devices back to the enterprise 340. IT will be able toforward events and log records into legacy management systems via SYSLOGand SNMP Traps.

The security engines 530 may perform weighted risk analysis. Forexample, the security engine 530 may analyze HTTP, FTP, SMTP, POP3, IM,P2P, etc. including any traffic arriving from the internet 330. Thesecurity engine 530 may assign a weight and rank for every object basedon its type, complexity, richness in abilities, source of the object,etc. The security engine 530 may assign weight based on the source usinga list of known dangerous or known safe sources. The security engine 530may assign weight to objects based on the category of the source, e.g.,a gambling source, an adult content source, a news source, a reputablecompany source, a banking source, etc. The security engine 530 maycalculate the weight, and based on the result determine whether to allowor disallow access to the content, the script to run, the systemmodification to occur, etc. The security engine 530 may “learn” usercontent (by analyzing for a predetermined period of time the generalcontent that the user accesses) and accordingly may create personalcontent profiles. The personal content profile may be used to calibratethe weight assigned to content during runtime analysis to improveaccuracy and tailor weighted risk analysis for specific usercharacteristics.

In some embodiments, the security engines 530, security policies 535 andsecurity data 540 may enable bypassing the mobile security system 345.The security policy 535, set by the security administrator 325, mayinclude a special attribute to force network connection through themobile security system 325 when outside the trusted enterprise 340.Thus, if this attribute is set “on,” when a mobile device 310 attemptsto connect to the internet 330 without the mobile security system 345and not from within the trusted enterprise 340, all data transferconnections including LAN connection, USB-net, modem, Bluetooth, WiFi,etc. may be closed. The mobile device 310 may be totally isolated andunable to connect to any network, including the internet 330.

In one embodiment, to enable this, when first connecting the mobilesecurity system 345 to the mobile device 310 using for example the USBcable (for both power and USB connection creation), the USB plug & playdevice driver will be sent into the mobile device 310. The installeddriver may be “Linux.inf” which allows a USB-net connection for themobile security system 345. This connection allows the mobile securitysystem 345 to access the internet 330 via the USB port and using themobile device 310 network connection plus additional code (“theconnection client”). In a Windows example, the connection client may beinstalled at the NDIS level of the mobile device 310 above all thenetwork interface cards of every network connection as shown in FIG. 6.The implementation will be as an NDIS Intermediate (IM) Driver orNDIS-Hooking Filter Driver. Both implementations may be at the kernellevel, so that an end user cannot stop or remove it. When starting themobile device 310, the connection client may attempt to connect to thesecurity administrator 325 or the network security system 320 locallywithin the trusted enterprise 340. If the node is not found (finding viaVPN is considered as not found in local LAN), the connection client willassume it is working from outside the trusted enterprise 340 and expectsto find the mobile security system 345 connected, e.g., via USB-net orother connection mechanism. If the mobile security system 345 is notfound, the connection client may avoid any communication to any networkconnection. By a policy definition, this behavior can be modified toallow communication to the enterprise 340 via VPN installed in themobile device 310. Similarly, in case of a mobile device system 345failure, all traffic may be disabled, except for the VPN connection intothe enterprise 340.

It will be appreciated that NDIS is one possible implementation ofintercepting traffic at the kernel level. For example, in anotherembodiment, the system may hook Winsock or apply other ways that may bein future Windows versions.

In an embodiment where the mobile security system 345 supports multiplemobile devices 310, the security engines 530, security policies 535 andsecurity data 540 may be different for each mobile device 310 (e.g.,based on for example user preferences or IT decision). Alternatively, itcan apply the same engines 530, policies 535 and data 540 for allconnected devices 310.

The remote management module 550 enables communication with securityadministrator 325 (and/or other security administrators), and enableslocal updating of security engines 530, security policies 535, securitydata 540 including signatures and other applications. In one embodiment,modification to the security policies 535 and data 540 can be done bythe security administrator 325 only. The remote management module 550 ofthe mobile security system 345 may receive updates from an updateauthorities device (UAD), e.g., on the security administrator 325 via asecured connection. A UAD may operate on an update server at a customerIT center located on the internet 330 to forward updates to mobilesecurity systems 345 that possibly do not belong to an enterprise 540 incharge of managing updates. A UAD may operate on a mobile securitysystem 345. Security engine 530 updates may modify the antivirus engineDLL, etc. OS and security application updates may be implemented onlyfrom within the enterprise 540 while connecting to the securityadministrator 325 and via an encrypted and authenticated connection.

The security administrator 325 can modify URL black and white lists forremote support to traveling users. In case of false positives, thesecurity administrator 325 may allow access to certain URLs, bybypassing the proactive heuristics security but still monitoring byfirewall, antivirus, IPS/IDS, etc. Additional remote device-managementfeatures may enable the security administrator 325 to perform remotediagnostics, access local logs, change configuration parameters, etc. onthe mobile security system 345. The security administrator 325 maydelegate tasks to a helpdesk for support.

The remote management module 550 may communicate with a wizard (e.g.,wizard 745), which may be on the security administrator 325, asillustrated in FIG. 7, or on another system. Details of the wizard 745and details of the communication schemes between the remote managementmodule 550 and the wizard 745 are described below with reference to FIG.7.

The distribution module 555 enables distribution of updates, e.g.,security policy 535 updates including rule updates, security data 540updates including signature updates, security engine 530 updates,application/OS updates, etc. by the mobile security system 345 to Nother mobile security systems 345. A routing table identifying the Nother mobile security systems 345 to whom to forward the updates may beprovided to the distribution module 555 to enable system 345 to system345 communication. Updates may be implemented according to policies setby the security administrator 325. When forwarding updates, thedistribution module 555 acts as a UAD.

Each mobile security system 345 may obtain its routing table withsecurity information updates, periodically, at predetermined times, uponlogin, etc. The routing tables may be maintained on a server, e.g., thesecurity administrator 325 or another mobile security system 345. In oneembodiment, the mobile security systems 345 may contact the server toretrieve the routing tables. Alternatively, the server may push therouting tables to the mobile security systems 345.

The distribution module 555 may enable rapid updates as shown in FIG. 9.Currently, all commercial antivirus products available do not updatedevices faster than viruses spread. To assure that a new virus attackdoes not spread faster than for example signature updates, each mobilesecurity system 345 may be an active UAD. In one embodiment, as shown inFIG. 9, each mobile security system 345 is responsible for forwardingthe signature updates to four other devices 345. As one skilled in theart will recognize, all devices 345 need to forward to the same numberof other devices 345. Multiple devices 345 may be responsible forforwarding to the same device 345. When necessary, offline devices 345being activated may poll the server, e.g., the security administrator325, for routing table updates. Many other updating techniques are alsopossible.

The backup module 560 may constantly backup image and changes of theboot sector and system files of the mobile device 310 into the flashmemory 520 or into another persistent memory device. That way, in caseof major failure, including a loss of the system or boot sector of themobile device 310, the mobile security system 345 may be identified as aCD-ROM during reboot and may launch the backup module (or separateprogram) to restore the boot sector and system files on the mobiledevice 310, thereby recovering the mobile device 310 without the needfor IT support. In an embodiment where the network security system 345supports multiple mobile devices 310, the backup module 560 may containseparate boot sector and system files for each of the mobile devices310, if different.

FIG. 7 is a block diagram illustrating details of a smart policyupdating system 700 in accordance with an embodiment of the presentinvention. System 700 includes the security administrator 325 coupled tothe network security system 320 and to the mobile security system 345.The network security system 320 includes security engines 705, includingan antivirus engine 715, an IPS/IDS engine 720, a firewall engine 725,and other security engines. The network security system 320 alsoincludes security policies and data 710, including antivirus policiesand data 730, IPS/IDS policies and data 735, firewall policies and data740, and other policies and data. Similarly, the mobile security system345 includes an antivirus engine 755, an IPS/IDS engine 760, a firewallengine 765, and other engines. The mobile security system 345 alsoincludes security policies and data 535/540, including antivirussecurity policies and data 770, IPS/IDS security policies and data 775,firewall security policies and data 780, and other security policies anddata.

The security administrator 325 includes a wizard 745 for enablingsubstantially automatic initial and possibly dynamic setup of thesecurity engines 530, security policies 535 and security data 540 on themobile security system 345. In one embodiment, the wizard 745 mayautomatically load all security engines 705 and policies and data 710 ofthe network security system 320 as the security engines 530 and policiesand data 535/540 on the mobile security system 345. In anotherembodiment, the wizard 745 may include all security engines 705 andpolicies and data 710 except those known to be irrelevant, e.g., thoserelated to billing software used by accounting, those relating to websoftware running only on the web servers, etc. In another embodiment,the engines 530 would need to be loaded by an IT manager, and would notbe loaded automatically by the wizard 745.

In one embodiment, the wizard 745 may determine whether the mobilesecurity system 345 requires a particular security engine 530, e.g., anantivirus engine 755, IPS/IDS engine 760, firewall engine 765, etc. Ifso determined, then the wizard 745 would load the engine 530 onto themobile security system 345. The wizard 745 would then determine whichpolicies and data sets, e.g., some for antivirus engine 755, some forthe IPS/IDS engine 760, some for the firewall engine 765, etc. areimportant to the mobile security system 345. The wizard 745 will thendetermine which of the antivirus policies and data 730 on the networksecurity system 320 are relevant to the antivirus policies and data 770on the mobile security system 345, which of the IPS/IDS policies anddata 735 on the network security system 320 are relevant to the IPS/IDSpolicies and data 775 on the mobile security system 345, which of thefirewall policies and data 740 on the network security system 320 arerelevant to the firewall policies and data 780 on the mobile securitysystem 345, and which of the other policies and data on the networksecurity system 320 are relevant to the policies and data on the mobilesecurity system 345. As stated above, the wizard 745 may determine thatall security engines 705 or just a subset are needed on the mobilesecurity system 345. The wizard 745 may determine that all policies anddata 710 for a given engine type or just a subset should be forwarded.The wizard 745 may determine which relevant policies and data 710 shouldbe forwarded to the mobile security system 345 based on rules developedby an IT manager, based on item-by-item selection during the setupprocedure, etc. Alternative to the wizard 745, an IT manager can setupthe engines 530 and policies and data 535/540 on the mobile securitysystem 345 without the wizard 745.

The security administrator 325 may also include an update authoritiesdevice 750. The update authorities device 750 may obtain security systemupdates (e.g., signature updates) and may send the updates to thenetwork security system 320 and to the mobile security system 345. Oneskilled in the art will recognize that the updates to the networksecurity system 320 and the updates to the mobile security system 345need not be the same. Further, the update authorities device 750 mayobtain the updates from security managers, security engine developers,antivirus specialists, etc. The update authorities device 750 mayforward the updates to all network security systems 320 and all mobilesecurity systems 345, or may forward routing tables to all mobilesecurity systems 345 and the updates only to an initial set of mobilesecurity systems 345. The initial set of mobile security systems 345 mayforward the updates to the mobile security systems 345 identified in therouting tables in a P2P manner, similar to the process illustrated inFIG. 9. As stated above, each mobile security system 345 operating toforward updates is itself acting as an update authorities device 750.

Other applications may be included on the mobile security system 345.For example, add-on applications for recurring revenue from existingcustomers may include general email, anti-spam, direct and secured emaildelivery, information vaults, safe skype and other instant messagingservices, etc.

Email Security and Anti-spam—implementation of mail relay on mobilesecurity systems 345 (including the web security engine above) and alocal spam quarantine (based on SendMail or similar process) mayimplement a complete mail security suite (SMTP and POP3) includinganti-spam with real time indexing (via online web spam quarries). Usersmay have access to the quarantine to review spam messages, releasemessages, modify and custom spam rules, etc., via a web interface.

Direct and Secured Email Delivery based on mail relay will allow themobile security system 345 to send user email directly from one mobilesecurity system 345 to another mobile security system 345 without usingin route mail servers. This allows corporate users to send emails thatneed not travel in the internet, thus leaving trace and duplicates ondifferent unknown mail servers in route. This combined with the abilityto use a secured pipe between two mobile security systems is valuable tocorporations. Without such methodology, people could trace emailsexchange without accessing to the enterprise's mail server, by trackingdown copies in intermediate mail servers that were used to deliver themessages.

Information Vault—Application to encrypt and store end user informationon the mobile security system 345 may be available only to authorizedusers via a web interface and a web server implemented on every mobilesecurity system 345 (e.g., BOA, Apache, etc.).

Safe Skype and Other IM—implementing an instant messaging client on themobile security system 345 can guarantee that the instant messagingsystem or P2P application has no access to data on the mobile device310. Adding a chipset of AC/97 to provide a sound interface on themobile security system 325 could allow users to talk and receive callsdirectly from/to the mobile security system 325.

Although not shown, a small battery may be included with the mobilesecurity system 345. This battery may be charged by the USB connectionduring runtime or using the power adapter at any time. The battery mayguarantee proper shutdown, e.g., when user disconnects the USB cablefrom the mobile security system 345. It will be signaled by the systemwhich will launch applications and system shutdown. This will ensure aproper state of the file system and flashing open files buffers.

A multi-layered defense and detection abilities is required. This may bedone by a special code that is constantly monitoring the scanning resultby different systems (antivirus, IDS/IPS, firewall, antispyware, URLcategory, etc.) and at different levels to build a puzzle and identifyan attack even if it's not recognized by each of the individualsubsystems. By doing this, the mobile security system 345 will maintainand in some cases even improve the security level provided within theenterprise 540.

One available benefit of the mobile security system 345 is its abilityto enforce the policy of the enterprise 540 on the end user while theyare traveling or working from home. Since the mobile security system 345uses similar security engines and policy as when connected from withinthe enterprise 540 and since the end user cannot access the internet 330without it (except via VPN connection into the enterprise 546), IT maybe capable of enforcing its security policy beyond the boundaries of theenterprise 540. The OS may be under the entire supervision of IT, whilethe mobile security system 345 OS acts as an end user OS under hiscontrol. This resolves the problems of who controls what and howsecurity and productivity face minimal compromise.

A standalone version of the mobile security system 345 may offer thesame functionality, and may provide a local management interface via webbrowser. Attractive to home users and small offices that lack an ITdepartment, the mobile security system 345 enables the end user tolaunch a browser, connect to the mobile security system 345, set thedifferent policies (update policy, security rules, etc.) includingmodifying the white and black URL lists, etc. There is also anopportunity to provide end users with a service of remote management ofthe mobile security systems 345 by subscription.

FIGS. 10A, 10B and 10C illustrate three example architectures ofconnecting a mobile security system 345 to a mobile device 310, inaccordance with various embodiments of the present invention. In FIG.10A, the mobile device 310 is coupled to the mobile security system 345via USB connections 1015 and 1020 and is coupled to the internet 330 viaa NIC card 1005. The mobile device 310 receives internet traffic fromthe internet 330 via its NIC card 1005. A kernel-level redirector 1010(e.g., via NDIS, Winsock, etc.) on the mobile device 310 automaticallyredirects the internet traffic via the USB connections 1015 and 1020 tothe mobile security system 345, which scans, cleans and returns thecleaned internet traffic to the mobile device 310 via the USBconnections 1015 and 1020. In FIG. 10B, the mobile device 310 is coupledto the mobile security system 345 via USB connections 1025 and 1030. Themobile security system 345 includes a NIC card 1035 for receivinginternet traffic from the internet 330. The mobile security system 345scans, cleans and forwards the internet traffic via the USB connections1025 and 1030 to the mobile device 310. In FIG. 10C, the mobile device310 is coupled to the mobile security system 345 via NIC cards 1040 and1045. The mobile security system 345 receives internet traffic from theinternet 330 via its NIC card 1045. The mobile security system 345scans, cleans and forwards the internet traffic wirelessly via the NICcards 1040 and 1045 to the mobile device 310. Other connectionarchitectures are also possible.

The foregoing description of the preferred embodiments of the presentinvention is by way of example only, and other variations andmodifications of the above-described embodiments and methods arepossible in light of the foregoing teaching. Although the network sitesare being described as separate and distinct sites, one skilled in theart will recognize that these sites may be a part of an integral site,may each include portions of multiple sites, or may include combinationsof single and multiple sites. The various embodiments set forth hereinmay be implemented utilizing hardware, software, or any desiredcombination thereof. For that matter, any type of logic may be utilizedwhich is capable of implementing the various functionality set forthherein. Components may be implemented using a programmed general purposedigital computer, using application specific integrated circuits, orusing a network of interconnected conventional components and circuits.Connections may be wired, wireless, modem, etc. The embodimentsdescribed herein are not intended to be exhaustive or limiting. Thepresent invention is limited only by the following claims.

The invention claimed is:
 1. A security system, comprising: securitysystem memory; a security system processor configured to: store in thesecurity system memory a security policy identifying one or more trustednetworks and defining when to forward network data intended for a mobiledevice to the mobile device for processing by at least one mobile deviceprocessor of the mobile device, the at least one mobile device processorof the mobile device being different than the security system processorof the security system, the security policy defining that when themobile device does not reside on any of the one or more trusted networksidentified by the security policy, the security system processor of thesecurity system will scan the network data for malicious content todecide whether the network data should be forwarded to the mobiledevice, the security policy defining that when the mobile device resideson any of the one or more trusted networks identified by the securitypolicy, the security system processor of the security system will allowthe network data to be forwarded to the mobile device without thesecurity system processor of the security system scanning for themalicious content; receive from the mobile device particular networkdata before the at least one mobile device processor of the mobiledevice processes the particular network data, the particular networkdata having been forwarded to the security system by the at least onemobile device processor of the mobile device; and execute security codeto implement the security policy as it relates to the particular networkdata received from the mobile device, the security code configured tomodify at least a portion of the particular network data beforedelivering the particular network data as modified to the mobile device.2. The security system of claim 1, wherein the security code isconfigured to perform gateway level security services including firewallservices.
 3. The security system of claim 1, wherein the security systemuses at least one of a USB connector, a PCMCIA connector, an Ethernetconnector, or a wireless communication module to communicate with themobile device.
 4. The security system of claim 1, wherein the securitycode includes at least one of antivirus software, antispyware software,a firewall, IPS/IDS software, content filtering software, a bytecodemonitor, and a URL monitor.
 5. The security system of claim 1, furthercomprising remote management code capable of receiving and installingsecurity policy updates.
 6. The security system of claim 1, furthercomprising remote management code capable of receiving and installingsecurity code updates.
 7. The security system of claim 1, furthercomprising remote configuration code capable of communicating with awizard, the wizard being in communication with an enterprise networksecurity system, the wizard capable of substantially automaticgeneration of the security policy based on one or more policies on theenterprise network security system.
 8. The security system of claim 1,wherein the security code is configured to prevent at least a portion ofthe particular network data from being processed by the mobile device.9. The security system of claim 1, wherein the mobile device includes akernel-level redirector configured to redirect the particular networkdata received from a network by the mobile device to the securitysystem.
 10. The security system of claim 1, wherein at least a portionof the security system is a part of the mobile device.
 11. A methodcomprising: storing in security system memory a security policyidentifying one or more trusted networks and defining when to forwardnetwork data intended for a mobile device to the mobile device forprocessing by at least one mobile device processor of the mobile device,the at least one mobile device processor of the mobile device beingdifferent than a security system processor of the security system, thesecurity policy defining that when the mobile device does not reside onany of the one or more trusted networks identified by the securitypolicy, the security system processor of the security system will scanthe network data for malicious content to decide whether the networkdata should be forwarded to the mobile device, the security policydefining that when the mobile device resides on any of the one or moretrusted networks identified by the security policy, the security systemprocessor of the security system will allow the network data to beforwarded to the mobile device without the security system processor ofthe security system scanning for the malicious content; receiving fromthe mobile device particular network data before the at least one mobiledevice processor of the mobile device processes the particular networkdata, the particular network data having been forwarded to the securitysystem by the at least one mobile device processor of the mobile device;and executing security code to implement the security policy as itrelates to the particular network data received from the mobile device,the executing the security code including modifying at least a portionof the particular network data before delivering the particular networkdata as modified to the mobile device.
 12. The method of claim 11,wherein the executing the security code includes performing gatewaylevel security services including firewall services.
 13. The method ofclaim 11, further comprising using at least one of a USB connector, aPCMCIA connector, an Ethernet connector, or a wireless communicationmodule to communicate with the mobile device.
 14. The method of claim11, wherein the executing the security code includes executing at leastone of antivirus software, antispyware software, a firewall, IPS/IDSsoftware, content filtering software, a bytecode monitor, and a URLmonitor.
 15. The method of claim 11, further comprising receiving andinstalling security policy updates.
 16. The method of claim 11, furthercomprising receiving and installing security code updates.
 17. Themethod of claim 11, further comprising communicating with a wizard, thewizard being in communication with an enterprise network securitysystem, the wizard capable of substantially automatic generation of thesecurity policy based on one or more policies on the enterprise networksecurity system.
 18. The method of claim 11, wherein the executing thesecurity code includes preventing at least a portion of the particularnetwork data from being processed by the mobile device.
 19. The methodof claim 11, wherein the receiving the particular network data from themobile device includes receiving the particular network data from akernel-level redirector configured to redirect the particular networkdata received from a network by the mobile device to the securitysystem.
 20. The method of claim 11, wherein at least a portion of thesecurity system is a part of the mobile device.
 21. A security systemcomprising: security system memory storing a security policy identifyingone or more trusted networks and defining when to forward network dataintended for a mobile device to the mobile device for processing by atleast one mobile device processor of the mobile device, the at least onemobile device processor of the mobile device being different than asecurity system processor of the security system, the security policydefining that when the mobile device does not reside on any of the oneor more trusted networks identified by the security policy, the securitysystem processor of the security system will scan the network data formalicious content to decide whether the network data should be forwardedto the mobile device, the security policy defining that when the mobiledevice resides on any of the one or more trusted networks identified bythe security policy, the security system processor of the securitysystem will allow the network data to be forwarded to the mobile devicewithout the security system processor of the security system scanningfor the malicious content; means for receiving from the mobile deviceparticular network data before the at least one mobile device processorof the mobile device processes the particular network data, theparticular network data having been forwarded to the security system bythe at least one mobile device processor of the mobile device; andsecurity code configured to implement the security policy as it relatesto the particular network data received from the mobile device, thesecurity code configured to modify at least a portion of the particularnetwork data before delivering the particular network data as modifiedto the mobile device.